Greptile Summary

This PR introduces Shared Components — environment-scoped, versioned pipeline component configurations that can be linked into multiple pipelines — along with a restructured Library page (replacing /templates with /library) that hosts both Templates and the new Shared Components section.

Key changes:

• New SharedComponent Prisma model with (environmentId, name) unique constraint, onDelete: SetNull FK on PipelineNode, and a version counter that increments on config edits.
• sharedComponentRouter — full CRUD (create, createFromNode, update, delete, acceptUpdate, acceptUpdateBulk, unlink, linkExisting). All procedures correctly apply withTeamAccess and withAudit middleware. saveGraph validates that all sharedComponentIds belong to the pipeline's own environment before writing.
• Flow store gains three new actions: patchNodeSharedData (no history push, intentionally amends the preceding addNode snapshot), acceptNodeSharedUpdate (pushes snapshot), unlinkNode (pushes snapshot). The fingerprint computation correctly excludes transient display fields (sharedComponentName, sharedComponentLatestVersion).
• Pipeline editor shows purple nodes/banners for linked components, amber update banners for stale nodes, and a right-click "Save as Shared Component" context menu action. save-shared-component-dialog.tsx correctly syncs the Zustand store after createFromNode succeeds.
• Copy/promote logic — copyPipelineGraph gains a stripSharedComponentLinks flag; promote passes true, clone does not. Template creation strips links via the templateNodeSchema Zod schema (which simply omits sharedComponentId).
• Pipeline list surfaces an amber "Updates available" badge with a tooltip listing the stale component names.

Minor issues found:

• acceptUpdateMutation and unlinkMutation in detail-panel.tsx are missing onError toast handlers, causing silent failure when the server returns an error.
• New /library/shared-components/ pages (list, detail, new) and the library layout are missing ErrorBoundary protection, per project conventions.

Confidence Score: 4/5

• PR is safe to merge — all previously flagged security issues have been addressed and the core feature logic is correct.
• The cross-environment injection vectors, TOCTOU race conditions, and missing store syncs called out in previous review rounds are all resolved in this iteration. The remaining findings are both minor: missing onError toast handlers (silent failure) and missing ErrorBoundary wrappers on the new library pages. Neither is a data-loss or security risk, but they affect user experience and crash resilience.
• src/components/flow/detail-panel.tsx — missing onError handlers on acceptUpdateMutation and unlinkMutation. New library pages under src/app/(dashboard)/library/shared-components/ — missing ErrorBoundary protection.

Important Files Changed

Entity Relationship Diagram

%%{init: {'theme': 'neutral'}}%%
erDiagram
    Environment {
        string id PK
        string name
    }
    SharedComponent {
        string id PK
        string name
        string componentType
        ComponentKind kind
        Json config
        int version
        string environmentId FK
        DateTime createdAt
        DateTime updatedAt
    }
    PipelineNode {
        string id PK
        string pipelineId FK
        string componentType
        ComponentKind kind
        Json config
        string sharedComponentId FK "nullable, SetNull on delete"
        int sharedComponentVersion "nullable"
    }
    Pipeline {
        string id PK
        string environmentId FK
        string name
    }

    Environment ||--o{ SharedComponent : "scopes"
    Environment ||--o{ Pipeline : "contains"
    Pipeline ||--o{ PipelineNode : "has"
    SharedComponent ||--o{ PipelineNode : "linked to (0..*)"

_{Last reviewed commit: 7b7e356}

@greptile fixed.

1. createFromNode — now validates node.pipeline.environmentId === input.environmentId to prevent
   cross-environment config leakage
2. update — lookup, name-conflict check, and write all wrapped in $transaction to prevent TOCTOU race
   producing unhandled P2002 errors

@greptile fixed.

1. saveGraph cross-environment injection — now validates all sharedComponentId values in the payload belong
   to the pipeline's environment before persisting
2. create TOCTOU race — duplicate-name check + create wrapped in $transaction, matching the createFromNode
   pattern

@greptile fixed

1. Mutations reverted on save — acceptUpdate and unlink now sync the Zustand flow store via dedicated
   acceptNodeSharedUpdate and unlinkNode actions, so saveGraph writes the correct values.
2. Undo/redo breaks shared linkage — Shared component drop now uses patchNodeSharedData store action
   instead of raw setState, so the patched data is included in the node state that addNode's history snapshot
   captures.
3. saveGraph FK gap — Now validates all sharedComponentId values were found in the DB before checking
   environment ownership, producing a clean BAD_REQUEST instead of an unhandled FK constraint error.

@greptile fixed.

The SaveSharedComponentDialog now calls patchNodeSharedData in onSuccess to sync the Zustand store — canvas immediately shows the purple border, read-only config, and shared banner without needing a page reload.